Persist the backend marker in auth.json on first login and honor it on
subsequent runs so we don't re-probe the OS keyring on every CLI
invocation. Also drop the write/delete side of the probe — getPassword
on a non-existent entry is enough to detect an unavailable backend and
avoids unnecessary Keychain access.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

The OS keyring is machine-global, so the unique
__APIFY_INTERNAL_TEST_AUTH_PATH__ per test only isolates auth.json, not
the keyring. After one test logged in, the leaked token made later
tests see getToken() return a value with no matching username/id and
throw "Corrupted local user info". useAuthSetup already pins in-process
tests to the file backend; do the same for the dist subprocesses
runCli spawns.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Previously, clearSecrets() was a no-op when the active backend was
'file', so a user who logged in normally and later set
APIFY_DISABLE_KEYRING=1 before running logout would leave their token
in the OS keyring with no in-CLI way to remove it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…in message

When the user explicitly opts out via APIFY_DISABLE_KEYRING=1, calling
the keyring "unavailable" and telling them to set the var they already
set is misleading. Split the file-backend branch into two: env-disabled
vs probe failure.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

… keyring

Scoping the keyring change down: stripping the entire proxy object from
the userInfo write in getLoggedClient also dropped proxy.groups, which
breaks the log_in_out API test that compares auth.json to the API user
response. Leave proxy in the file as it was before and exclude the
internal secretsBackend marker from the test comparison.

- Move `ensureApifyDirectory` from utils.ts to files.ts to break the
  credentials.ts <-> utils.ts circular import.
- Drop the synthetic write/read/delete probe at backend selection time
  and treat the first real keyring write as the probe. On failure,
  downgrade to the file backend and persist the marker so future runs
  skip the keyring entirely. Avoids a duplicate macOS Keychain prompt
  on first login.
- Reword the "Corrupted local user info" error to accurately describe
  the stale-keyring-without-metadata state.

The shared runId in the runs lifecycle test points at a hello-world
actor that finishes in well under a second. After the resurrect step,
the abort CLI's startup overhead (1–3s) meant the resurrected run had
typically already SUCCEEDED by the time abort fired its API call,
causing abort to print `Error: Run with ID "..." is already aborted.`
to stdout with exit code 0 — which then broke `JSON.parse` in the test.

Start a dedicated abort target run with a 30s `sleepMs` input so the
abort always wins the race. Teach the basic test actor to honor the
new `sleepMs` input.

…al-storage' into 1115-use-os-keyring-for-credential-storage

The function only deletes keyring entries; auth.json cleanup is the caller's
responsibility (logout rimrafs the whole file). Renaming makes the scope
honest and avoids misleading future callers.

…rite

…rameter

Avoids the param-reassignment smell in getLoggedClient and
getApifyClientOptions. oxlint's no-param-reassign rule is currently
disabled in config; enabling it broadly is left for a follow-up.

Factor out hasUserMetadata so the stale-credentials branch reads
directly. Behaviorally identical to the previous two-stage check.